https://blue-build.org/ logo
Powered by
Installing intel vTune issue
# questions
j
Hey everyone, i added the intel vtune repo and installed the package, but its not anywhere on my machine. when i do 
rpm -qa | grep intel-oneapi-vtune
, it shows up, and when i try to do 
rpm-ostree install intel-oneapi-vtune
, it says 
error: "intel-oneapi-vtune" is already provided by: intel-oneapi-vtune-2025.3.0-15.x86_64. Use --allow-inactive to explicitly require it.
But when I try to uninstall it, i get 
error: Package/capability 'intel-oneapi-vtune' is not currently requested
. anyone know how to fix this?
a
message has been deleted
g
This might be a package that installs into 
/opt
. You'll want to use the 
optfix
part of the 
dnf
or 
rpm-ostree
module
You'd need to know the name of the directory it creates
j
oh yeah it is
ill give 
optfix
a try
g
What is vtune?
j
profiler for c++, rust and other languages
its pretty powerful, im using it in a distrobox rn but it also has some special kernel driver which makes it better
i wonder if you could detect if a package is trying to use 
/opt
and warn about it
or maybe its already doing that and i missed it
g
I was just thinking about that, maybe even looking into possibly fixing it automatically
We already have a systemd unit to recreate the symlinks
j
I know rpm -qi gives all the directories the package uses
Maybe you could use that, I have no idea how feasible it is lol
s
?
like, in a list
if so, smthn like "rpm -qi package | grep /opt" might work
idk what the nushell equivalent would be
j
I think it would be something like rpm -qi package | find —regex “^/opt”
x
i would probably split the output by row and filter the resulting list, but regex of course works always too
j
Regex 🥰🥰😍😍🔥💪💪
It makes it easy to make sure /opt isn’t somewhere in the middle
s
rpm -qi package | grep '^/opt'
j
so ive run into another issue... the vtune kernel driver isnt signed. it looks like if i have 
kernel-devel
installed and symlink it to the directory that intel looks for (it looks for 
/usr/src/linux-<version>
but fedora puts it in 
/usr/src/kernels/linux-<version>
), it will automatically build the kernel drivers. i was wondering what the best way would be to sign the drivers myself and install them in my blue-build image. intel provides a script to load the drivers on boot but im guessing that wont work on silverblue. Theres this tutorial https://www.jviotti.com/2024/10/08/running-the-intel-vtune-profiler-on-fedora.html that discusses how to do it on normal fedora.
PreviousNext
Powered by